Change SSE transport to streaming transport for MCP samples #216
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR migrates the MCP (Model Context Protocol) samples from SSE transport naming to streaming transport by renaming projects and namespaces as requested in the issue.
Changes Made
Project Renaming
McpSample.AspNetCoreSseServer
project toMcpSample.AspNetCoreServer
aspnetsseserver
toaspnetserver
Namespace Updates
Tools/Jokes.cs
andTools/WeatherTool.cs
fromMcpSample.AspNetCoreSseServer
toMcpSample.AspNetCoreServer
Transport Configuration
HttpTransportMode.StreamableHttp
for the new streaming transport modeTechnical Details
The migration maintains the
SseClientTransport
class usage (which appears to be kept for API compatibility) but ensures it's configured withHttpTransportMode.StreamableHttp
to use the new streaming transport mechanism instead of traditional Server-Sent Events.All projects build successfully and the MCP server starts correctly, confirming the migration maintains full functionality while removing SSE naming references as requested.
Fixes #215.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.